SE-0492: Add support for closures (with no captures) into @section expressions #85530
+72
−9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kubamracek
requested review from
hborla,
slavapestov and
xedin
as code owners
Contributor
Author
|
@swift-ci please test |
Contributor
Author
|
@swift-ci please test Windows platform |
DougGregor
approved these changes
Nov 17, 2025
| // Closures are allowed if they have no captures | ||
| if (auto closureExpr = dyn_cast<ClosureExpr>(expr)) { | ||
| TypeChecker::computeCaptures(const_cast<ClosureExpr *>(closureExpr)); | ||
| if (!closureExpr->getCaptureInfo().isTrivial()) { |
Member
There was a problem hiding this comment.
Ah, that came out nicer than expected.
Contributor
Author
|
@swift-ci please test Windows platform |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given that we support named function references, closures with no-captures are no different from that. Adding this mainly to be able to support macro-generated metadata, e.g. for Swift Testing.